Method for detecting video tiling

ABSTRACT

A method for detecting errors on an audio/video (A/V) data stream in a data service network includes providing multicast components operably coupled to each other via respective links for transmitting the A/V data stream to a user and for defining at least one multicast tree. The method further includes generating a state information signal indicative of a number of errors on the A/V data stream for at least one of the links and at least one of the plurality of multicast components. The method further includes determining the cumulative number of errors on the A/V data stream that are indicative of the number of errors for the at least one of the links and the at least one of the plurality of multicast components in the multicast tree in response to the state information signal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/049,511, filed Mar. 17, 2008, hereby incorporated by reference as toits entirety.

BACKGROUND

1. Field of the Invention

The embodiments of the invention described herein generally relate to amethod for detecting errors on a data stream that may cause video tiles.

2. Background Art

Video tiling is generally defined as blocks or other such impairmentspresent in a video output while displayed which distort a picture thatis intended for viewing by a user. Service providers such as video andhigh speed data service providers struggle in determining the source ofthe tiles. Video tiling causes customers to believe there are problemswith video receivers provided by the service providers. Customers oftenplace service calls with the service providers and require the serviceproviders to inspect and replace the video receivers in the customer'sresidence or place of business if the video tiling in the video outputis substantial. In some cases, the video receiver may be functioningproperly, but is nonetheless switched with another video receiver sincethe service provider is unable to determine the origin of errors withina multicast tree that cause video tiling.

A service provider network may include a number of multicast trees. Anygiven multicast tree in the network may include one or more videoreceivers operably coupled to one or more routers and one or moretransmission sources. The video receivers, routers, and transmissionsources are generally coupled to each via fiber links which span largedistances. The transmission source transmits an audio/video (A/V) datastream to the routers via the links. The routers, in turn, direct theA/V data stream over the links to other routers or various videoreceivers. It is not uncommon while transmitting the A/V data stream forerrors which produce video tiling to occur at the transmission source,the router, or the receiver. Such errors may also occur at the variouslinks coupled between the transmission source, routers, and receiverslocated in the multicast tree. Existing approaches are not capable ofproviding service technicians the ability to determine the origin oferrors in a multicast tree.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the present invention described herein are recitedwith particularity in the appended claims. However, other features willbecome more apparent and the embodiments of the present invention may bebest understood by referring to the following detailed description inconjunction with the accompany drawings in which:

FIG. 1 depicts a system for detecting video tiles in accordance to oneembodiment of the present invention;

FIG. 2 depicts a logical representation of a multi cast tree generatedby the error detection device;

FIG. 3 depicts a method for displaying and reporting the number of errorevents detected by the system of FIG. 1; and

FIG. 4 depicts a method for detecting the root cause of the video tilesdetected by the system of FIG. 1.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

FIG. 1 depicts a system 10 for detecting video tiling in accordance toone embodiment of the present invention. The exemplary system 10includes a plurality of multicast trees 12 ₁-12 _(M) and an erroridentification device 14. For any given data service network, a serviceprovider may provide audio visual data or high speed data to theplurality of multicast trees 12 ₁-12 _(M). Specific multicast trees maybe designated to transmit audio visual data to various zones or regionswithin a particular country. Each multi cast tree 12 includes atransmission source 16 (12 ₁ has 16 ₁, 12 ₂ has 16 ₂ . . . 12 _(M) has16 _(M)). The transmission source 16 is adapted to generate an A/V datastream. The A/V data stream comprises a plurality of packets. Eachpacket may include video or audio data (or both).

A plurality of routers 18 ₁-18 _(N) are adapted to receive the A/V datastream from each of the source 16 _(M). A plurality of receivers 20 ₁-20_(O) are operably coupled to the routers 18 ₁-18 _(N). In theillustrated example, the router 18 ₁ directs the A/V data stream to thereceiver 20 ₁. The router 18 _(N) directs the A/V data stream to thereceivers 20 ₂ and 20 _(O). The receivers 20 ₁-20 _(O) are adapted topresent the A/V data to an end user for viewing. The source 16 ₁,routers 18 ₁-18 _(N), and receivers 20 ₁-20 _(O) are generally definedas multicast components within the multicast tree 12 ₁ and co-act witheach other to transmit the A/V data stream to an end viewer. In general,all references made specifically to the multicast tree 12 ₁ generallyapply equally to the multicast trees 12 ₂-12 _(M). For example, eachmulticast tree 12 ₂-12 _(M) may include any number of multicastcomponents such as the transmission source, the routers, and thereceivers. It is generally understood that each multi cast tree 12 ₁-12_(M) may include different or equal amounts of sources, routers, andreceivers from one another. Further, the particular arrangement of thesources, routers, and receivers may vary or be similar to one anotherfor each multicast tree 12 ₁-12 _(M).

Each multicast component (e.g., 16, 18 ₁-18 _(N), and 20 ₁-20 _(O)) inthe multicast trees 12 ₁-12 _(M) are operably coupled together via aplurality of fiber links 19 ₁-19 _(P). With respect to the exemplarymulticast tree 12 ₁, the source 16 ₁ and the router 18 ₁ are coupledtogether via the link 19 ₁. The router 18 ₁ and the receiver 20 ₁ areoperably coupled together via the link 19 ₂. The source 16 ₁ and therouter 18 _(N) are operably coupled together via the link 19 ₃. Therouter 18 _(N) and the receiver 20 ₂ are operably coupled together viathe link 19 ₄. The router 18 _(N) and the receiver 20 _(O) are operablycoupled together via the link 19 _(P). In general, each multicastcomponent transmits the A/V data stream to the next multicast componentdownstream in the trees 12 ₁-12 _(M) via a corresponding link.

In addition, each receiver coupled to the source via a particular routeris generally defined as a path within a given multicast tree 12 ₁-12_(M). In the illustrated embodiment, the multicast tree 12 ₁ includes atotal of three paths. The source 16 ₁, the link 19 ₁, the router 18 ₁,the link 19 ₂, and the receiver 20 ₁ form a first path. The source 16 ₁,the link 19 ₃, the router 18 _(N), the link 19 ₄, and the receiver 20 ₂form a second path. The source 16 ₁, the link 19 ₃, the router 18 _(N),the link 19 _(P), and the receiver 20 _(O) form a third path. Ingeneral, each multicast tree 12 ₁-12 _(M) is generally adapted toinclude one or more paths for transmitting the A/V data stream to a userfor viewing. Each link or path within a corresponding multicast tree 12₁-12 _(M) may span thousands of kilometers for a given region or part ofthe country. Errors attributed to the transmission of the A/V datastream within the network (e.g., from a source to a router and/or from arouter to a receiver via corresponding links) in any given path maygenerate errors that may cause video tiling at a given receiver. Inaddition, a number of video impairments (or video tiling) may be due tofabric errors. Each router generally includes one or more interfaces (orline cards). A fabric (or communication path) is generally presentbetween all line cards. Video tiling events may be caused due toproblems on the fabric(s) present between the line cards. In someinstances, the fabric may include intermittent transmission problems.Such problems may cause packet corruption or lead to packet(s) beingdropped as the packet is transmitted from one line card to another(e.g., all line cards internal to the same router).

The error identification device 14 is operably coupled to the multicasttrees 12 ₁-12 _(M) via a data communication line 17. The erroridentification device 14 is configured to determine the cumulativenumber of errors present within each link, path, and/or router of themulticast trees 12 ₁-12 _(M) so that service technicians can determinethe growth of errors in a particular multicast tree 12 ₁-12 _(M) overany period of elapsed time. As note above, errors related to the routermay be fabric errors. Such errors (transmission errors on the linksand/or paths, and fabric errors associated with the routers) maycontribute to the presence of video tiling at a receiver. With respectto the multicast tree 12 ₁, each router 18 ₁-18 _(N) is configured totransmit a state information signal for every directly connected link inthe multicast tree 12 ₁ to the error identification device 14 via thedata communication line 17.

The state information signal includes the number of packets transmittedand received from each multicast component (e.g., 16 ₁, 18 ₁-18 _(N), 20₁-20 _(O)) for the corresponding link and the number of packets receivedat each multicast component over the corresponding link with an errorfor every path in the multicast tree 12 ₁. For example, the router 18 ₁may provide the number of packets successfully transmitted from thesource 16 ₁ to the router 18 ₁ and the number of packets with errorsreceived by the router 18 ₁ to the error identification device 14 withthe state information signal. The router 18 ₁ may also provide thenumber of packets transmitted from the router 18 ₁ to the receiver 20 ₁with an error to the error identification device 14 with the stateinformation signal.

In addition, the router 18 ₁ may also include the number of packets thatmay be dropped due to errors in the state information signal. Sucherrors may be due to transmission issues (e.g., cyclic redundancy check(CRC) errors), interface overruns (e.g., contention for resources withinthe routers), transmission issues within each router (e.g., switchfabric errors), or output drops which are caused due to excessive loadson the transmitting interface. The router 18 ₁ obtains packet countinformation (e.g., packets lost due to CRC errors, fabric issues, etc.).As noted above, each router 18 ₁ and 18 _(N) generally includes a numberof interfaces. Multicast content (e.g., A/V data stream) may flow overany one or more of the interfaces to a corresponding router 18 ₁ and 18_(N). The routers 18 ₁ and 18 _(N) perform a CRC error coding schemewhich adds redundant bits within the packets of the A/V data stream toindicate which packets in the A/V data stream includes an error for aparticular multicast component.

CRC is generally defined as the process whereby a transmitting deviceembeds a calculation value along with audio and visual data in a packetin a data stream prior to transmitting the data stream. The receivingdevice repeats a similar calculation to obtain the similar calculationvalue for comparing the value embedded with the audio and video data ina packet after transmitting the data stream. If both the transmittingdevice and the receiving device obtain the same result, the particularpacket transmitted is assumed to be error free. If the receiving deviceobtains a different result from that of the transmitting device, anerror is presumed to have occurred and the packet is discarded.

In general, the routers 18 ₁ and 18 _(N) determine when an interfacethat belongs to a multicast component drops a packet. The routers 18 ₁and 18 _(N) may be configured to report abstract errors which may resultin packets being dropped. Such errors may be related to errors on thelink or errors associated with the routers 18 ₁ and 18 _(N). Each router18 ₁ and 18 _(N) is periodically queried by the error identificationdevice 14 to transmit the state information signal over the datacommunication line 17 to the error identification device 14.

Each router 18 ₁-18 _(N) is also periodically queried by the erroridentification device 14 to transmit an identification signal over thedata communication line 17 to the error identification device 14. Router18 ₁ is generally configured to track packet data received andtransmitted on interfaces belonging to the router 18 ₁. Likewise, therouter 18 _(N) is generally configured to track packet data received andtransmitted on interfaces that belong to the router 18 _(N). In general,each router 18 ₁ and 18 _(N) provides a local view of the multicast treeby tracking corresponding interfaces (e.g., which belong to each router18 ₁ and router 18 _(N), respectively) for incoming and outgoing packetsof multi cast content. Each router 18 ₁ and 18 _(N) transmits thetracked incoming and outgoing packets on a given interface over theidentification signal to the error identification device 14. The erroridentification device 14 includes a correlation engine 22 for assemblingthe local views provided by each router 18 ₁ and 18 _(N) into a singleend-to-end view (e.g., from source to receiver across each path) togenerate an electronic logical representation of the multicast tree 12₁. In response to generating the logical representation of the multicasttree 12 ₁ (e.g., determining corresponding paths from the source toevery receiver), the correlation engine 22 also associates the number ofpackets lost due to error.

The routers 18 ₁-18 _(N) are adapted to provide the tracked incoming andoutgoing packets on a given interface by executing a protocolindependent multicast (PIM) and an internet group membership protocol(IGMP). IGMP is generally defined as a signaling protocol that is usedby any one or more of the receivers to express interest in a particularmulticast group to a corresponding router. The router 18 ₁-18 _(N) usethe PIM to build the multicast tree 12 ₁-12 _(M) from the receiver backto the transmission source. In general, the routers themselves may notunderstand what a particular multi cast tree looks like from the sourceto all receivers. Instead, a single router (or each router) understandsthe particular interface on which a specific multicast feed is expectedto arrive and the interfaces the single router is expected to transmitthe multicast content on. The correlation engine 22 gathers thisinformation in response to querying the routers 18 ₁-18 _(N). Thecorrelation engine 22 processes and combines this per router informationinto an end-to-end logical representation for each multicast tree 12-12.A user interface visually displays the logical representation for themulticast tree.

A database 24 is coupled to the error identification device 14 forstoring information received via the state information signal and theidentification signal. The error identification device 14 is adapted tocalculate the cumulative number of errors for any link or path over apredefined time frame in response to receiving the state informationsignal. The error identification device 14 determines the cumulativenumber of errors based on errors present in the links, paths and/or therouters. The predefined time frame may correspond to the last N hours ordays. The error identification device 14 is further configured toassociate the cumulative number of errors for each link and path in themulticast trees 12 ₁-12 _(M) after generating the logical representationfor each multicast tree 12 ₁-12 _(M). This characteristic will bediscussed in more detail in connection with FIG. 2. The erroridentification device 14 allows a user to select a corresponding timeframe (e.g., 1 hour, 7 hours, 24 hours, or 7 days) to view thecumulative number of errors for each link and path (via the usermulticast component) within a particular multicast tree 12 ₁-12 _(M).The errors may be caused or attributed to various overdrive conditionsat the multicast components within the routers, or by problematic fiberlinks in the network.

In general, the source 16 ₁ and the receivers 20 ₁-20 _(O) areconfigured to generate alerts as simple network management protocol(SNMP) traps in response to detecting errors while receiving theincoming A/V data stream. The source 16 ₁ and/or the receivers 20 ₁-20_(O) transmit the alerts to the correlation engine 22 in response todetecting errors in real time (or asynchronously). The alerts generatedby the source 16 ₁ and/or the receivers 20 ₁-20 _(O) may be indicativeof whether a surge of errors are occurring over the network and whetherthere may be any new errors on any multicast component of the path fromthe source to the receiver. The correlation engine 22 receives thealerts and determines the particular multicast tree 12 ₁-12 _(M) that isimpacted and displays such information to service personnel. In responseto receiving the alerts, the correlation engine 22 may confirm theoperational integrity of the affected multicast component, link or pathin any or all of multicast trees 12 ₁-12 _(M). If errors on the pathfrom the source to the receiver are confirmed and are temporally alignedwith the alerts, then the correlation engine 22 may be adapted to alertservice personnel as to the root cause of the errors to allow supportpersonnel to fix or minimize the impact of the link or router errors.

FIG. 2 depicts an example of a logical representation of a multicasttree 12′ generated by the error identification device 14. The multicasttree 12′ includes a source 16′, a plurality of routers 18 ₁′-18 _(N)′,and a plurality of receives 20 ₁′-20 _(O)′. The source 16′, routers 18₁′-18 _(N)′, and receivers 20 ₁′-20 _(O)′ are coupled to each other viaa plurality of links 19 ₁′-19 _(P)′. FIG. 2 illustrates that the link 19₁′ exhibits 56 errors over the last two hour period, 56 errors over thelast four hour period, 143 errors over the last twenty-four hour period,and 1017 errors over the last seven day period. No additional errorswere detected with respect to links 19 ₂′-19 ₈′. FIG. 2 depicts thedetection of 784 errors over the last seven day period and no errors forthe last two, four, and twenty-four hour periods for the link 19 _(P)′.In response to detecting number of errors for the link 19 _(P)′, theerror identification device 14 determines that the cumulative number oferrors for the path (e.g., 19 ₁′-19 _(P)′) is 56 errors for the last twohour period, 56 errors for the last four hour period, 143 errors for thelast twenty-four hour period, and 1801 errors for the last seven dayperiod. The errors visually displayed next to each link of FIG. 2 may becaused due to issues or errors related to the links, paths, and/or therouters.

FIG. 3 depicts a method 50 for displaying and reporting errors asdetected by the system 10. In general, the method 50 is to be executedprior to utilizing the correlation engine 22 to receive alerts from thesource 16 ₁ and the receivers 20 ₁-20 _(O).

In block 52, the error identification device 14 receives theidentification signal from the routers in each multicast tree 12 ₁-12_(M).

In block 54, the error identification device 14 (or the correlationengine 22) creates a logical representation for each multicast tree 12₁-12 _(M) (including all applicable multicast components and links) inresponse to the identification signal transmitted by the routers. Forexample, the error identification device 14 maps and derives all of theend-to-end paths for each multicast tree 12 ₁-12 _(M).

In block 56, the error identification device 14 determines the number oferrors on each link 19 ₁-19 _(P) for a predefined time frame (e.g., 2hours, 4 hours, 24 hours, 7 days, etc.).

In block 58, the error identification device 14 considers every path(e.g. from the source down to the receiver) in each multicast tree 12₁-12 _(M) to compute the cumulative number of errors for each path(which includes errors caused by the links, paths, and/or routers) ineach multicast tree 12 ₁-12 _(M).

In block 60, the error identification device 14 outputs the visuallogical representation for each multicast tree 12 ₁-12 _(M) via the usermulticast component. The visual logical representation depicts thecumulative number of errors at each link and path for a predefined timeframe.

In block 62, the error identification device 14 generates a web listingfor each receiver impacted by the cumulative errors and sorts thereceivers based on the number of errors detected per receiver. The erroridentification device 14 may generate the web listing into a color-codedmatrix which indicates hot spots or potential problem areas for eachmulticast component in the multicast tree 12 ₁-12 _(M) that may begenerating errors which result in video tiling. The user multicastcomponent visually displays the listing.

FIG. 4 depicts a method 70 for receiving alerts based on errors presentin the A/V data stream. The method 70 is generally executed after theerror identification device 14 generates the logical representation foreach multi cast tree 12 ₁-12 _(M).

In block 72, the correlation engine 72 is adapted to receiveasynchronous (or event based) alerts or notifications from any one ormore of the sources or receivers in the multicast trees 12 ₁-12 _(M) anytime such errors are detected by the sources or receivers.

In block 74, the correlation engine 22 determines which multicast tree12 ₁-12 _(M) from the logical representation of the multicast trees 12₁-12 _(M) includes a source or receiver that detects errors associatedwith the A/V data stream.

In block 76, the correlation engine 22 consults the logicalrepresentation for the affected multicast tree 12 ₁-12 _(M) asidentified in block 74 to determine the corresponding paths from thesource to each receiver for the affected multicast trees 12 ₁-12 _(M).

In block 78, the correlation engine 22 performs a real-time query on theapplicable paths identified in block 76 to determine if there has beenany recent network events which triggered the sources or receivers totransmit the alerts as noted in connection with block 72. Such networkevents may include hard or soft failures. The hard failures may includefiber line cuts, xenpack failures, transport issues, or centralprocessing unit (CPU) spikes. The soft failures may include marginalxenpack transports, loose or dirty connections, or various componentoverloads (e.g., such overloads may be associated with applicationspecific integrated circuits (ASICs), line cards, or fabric fibers).

In block 80, the correlation engine 22 attempts to determine the rootcause for the errors based on whether recent network events (e.g., hardor soft failures) are detectable. If a recent network event (e.g., hardor soft failure) is detected, the method 70 moves to block 82. If arecent network event cannot be detected, the method 70 moves to block84.

In block 82, the correlation engine 22 outputs the location (e.g., linkand path) and the type of network event responsible for creating theerror associated with the A/V data stream via the user multicastcomponent.

In block 84, the correlation engine 22 determines that the root causefor the errors may be attributed with a particular transmission sourcein the affected multicast tree 12 ₁-12 _(M) or with the actual contentthat is flowing into a particular transmission source. In such a case,the correlation engine 22 outputs via the user multicast component thata network event was not detected and that the problem may be with aparticular transmission source or the data flowing into the transmissionsource.

The embodiments of the present invention provide for an erroridentification device 14 which is capable of mapping multicastcomponents, links, and paths for each multicast tree 12 ₁-12 _(M). Theerror identification device 14 is further adapted to receive the stateinformation signal and the identification signal from routers 18 ₁-18_(N) within each multi cast tree 12 ₁-12 _(M) to determine thecumulative number of errors per link and the cumulative number of errorsper path and to provide a logical representation of such data (e.g.,such errors may be attributed to the links, paths and/or the routers).The error identification device 14 provides the logical representationof the multicast trees 12 ₁-12 _(M) and the cumulative number of errorsper link and path to allow service technicians to diagnose andtroubleshoot problem areas based on the cumulative number of errorsshown in the logical representation. In response to the erroridentification device 14 generating a logical representation of themulticast trees 12 ₁-12 _(M), the correlation engine 22 monitors thesources 16 ₁ and the receivers 20 ₁-20 _(O) in real-time for erroralerts associated with the transmission of the A/V data stream. Inresponse to such alerts, the correlation engine 22 provides servicetechnicians the ability to determine the number of errors impacting eachof the multicast trees 12 ₁-12 _(M) in real time before the errorsassociated with the transmission of the A/V data stream through thevarious links and paths grow into major problems. Such capability allowsservice technicians to troubleshoot and fix errors that may cause videotiling and may minimize exposure of the video tiling for the user.

While embodiments of the present invention have been illustrated anddescribed, it is not intended that these embodiments illustrate anddescribe all possible forms of the present invention. Rather, the wordsused in the specification are words of description rather thanlimitation, and it is understood that various changes may be madewithout departing from the spirit and scope of the present invention.

What is claimed is:
 1. A method, comprising: receiving, by at least one computing device from an error-reporting device of a network, a message indicating that at least one error associated with a data stream has been detected at the error-reporting device receiving the data stream; determining, by the at least one computing device, a path through which the data stream is transmitted, the path being associated with the error-reporting device based on a logical representation of a multicast tree, comprising a plurality of paths, of the network; determining, for each link of a plurality of links of the path, a cumulative number of errors detected during each overlapping time period of a plurality of overlapping time periods having different lengths; and outputting data representative of the respective cumulative number of errors and the corresponding overlapping time period, of the plurality of overlapping time periods, for each link of the plurality of links of the path.
 2. The method of claim 1, further comprising: determining a cumulative number of errors detected at each receiver, of a plurality of receivers of the network, for a predetermined time period, wherein one receiver is the error-reporting device; sorting the plurality of receivers based on the cumulative number of errors detected at each receiver; and causing an output of an indication of an error hotspot based on the sorting.
 3. The method of claim 1, further comprising determining whether a link, of the plurality of links of the path, is associated with one or more error-causing events.
 4. The method of claim 1, wherein the message comprises an asynchronous message sent by the error-reporting device in response to the error-reporting device detecting the at least one error.
 5. The method of claim 4, further comprising: determining, based on the cumulative number of errors detected during each overlapping time period for each link, a cumulative number of errors detected during each overlapping time period of the plurality of overlapping time periods for the path.
 6. The method of claim 1, wherein the at least one error detected at the error-reporting device is video tiling.
 7. A method, comprising: generating, for each multicast tree of a plurality of multicast trees of a network, a logical representation of a plurality of paths in the respective multicast tree; receiving, by at least one computing device from an error-reporting device of the network, a message indicating that at least one error associated with a data stream has been detected at the error-reporting device receiving the data stream; determining a multicast tree of the plurality of multicast trees affected by the at least one error; determining a path of the plurality of paths of the multicast tree affected by the at least one error; determining, for each link of a plurality of links of the path, a plurality of cumulative number of errors respectively detecting during a plurality of overlapping time periods having different lengths; and outputting data representative of the respective cumulative number of errors and the corresponding overlapping time period, of the plurality of overlapping time periods, for each link of the plurality of links of the path.
 8. The method of claim 7, further comprising: determining a cumulative number of errors detected at each receiver, of a plurality of receivers of the network, for a predetermined time period, wherein one receiver is the error-reporting device; sorting the plurality of receivers based on the number of cumulative errors detected at each receiver; and causing an output of an indication of an error hotspot based on the sorting.
 9. The method of claim 7, further comprising determining whether a link, from the plurality of links of the path, is associated with one or more error-causing events.
 10. The method of claim 7, wherein the at least one error is caused by one or more of a damaged communication line, a loose connection, or an overloaded device.
 11. A method comprising: receiving, by a computing device from a receiver of a network comprising a multicast tree, an alert indicating that at least one error associated with a data stream has been detected at the receiver receiving the data stream; determining, by the computing device, a path through which the data stream is transmitted, the path being associated with the receiver based on a logical representation of the multicast tree comprising a plurality of paths; determining, for each link of a plurality of links of the path, a plurality of cumulative number of errors respectively detected during a plurality of overlapping time periods having different lengths; and outputting data representative of the respective cumulative number of errors and the corresponding overlapping time period, of the plurality of overlapping time periods, for each link of the plurality of links of the path.
 12. The method of claim 11, further comprising: determining a different path that is affected by the at least one error; determining, for each link of a plurality of links of the different path, a different plurality of cumulative number of errors respectively detected during the plurality of overlapping time periods; and outputting data representative of the different plurality of cumulative number of errors.
 13. The method of claim 11, further comprising: determining, based on the plurality of cumulative number of errors respectively detected during the plurality of overlapping time periods for each link, a plurality of cumulative number of errors detected on the path.
 14. The method of claim 11, further comprising: determining a cumulative number of errors detected at each receiver, of a plurality of receivers of the network, for a predetermined time period; sorting each receiver of the network based on the cumulative number of errors detected at each receiver for the predetermined time period; and causing an output of an indication of an error hotspot based on the sorting.
 15. The method of claim 14, wherein the indication of the error hotspot is a color-coded listing of each receiver of the network.
 16. The method of claim 11, further comprising: determining whether an event causing the at least one error occurred on the path; and in response to determining that the event occurred on the path, causing an output of a location of a link, of the plurality of links of the path, that is responsible for creating the at least one error.
 17. The method of claim 16, wherein the event is a damaged communication line. 